The METALIB procedure enables you to import or register tables from a SAS library or a database library into the SAS Metadata Repository. This procedure provides a programmatic approach to import or register tables as an alternative to doing this task manually via SAS^® Management Console. As is the case when you manually import tables, PROC METALIB stores metadata about the physical tables. The procedure does not store the underlying data tables in the SAS Metadata Repository.

When the database table contains an index that is created by an expression rather than from a physical column, PROC METALIB generates the following Read access violation:

ERROR:  Read Access Violation In Task  [ METALIB ]

Exception occurred at (63434395)
Task Traceback
Address   Frame     (DBGHELP API Version 4.0 rev 5)
63434395  090BF2BC  sasmetas:mcn_main+0x13395
634322D5  090BF528  sasmetas:mcn_main+0x112D5
6342EBFA  090BF7FC  sasmetas:mcn_main+0xDBFA
63422978  090BFF8C  sasmetas:mcn_main+0x1978
015C2854  090BFFA0  sashost:Main+0xC290
016AE038  090BFFB4  sashost:Main+0xF7A74
7C80B713  090BFFEC  kernel32:GetModuleFileNameA+0x1B4

For example, this statement creates an index from an expression rather than a physical column in a database table:

create index IDXNAME on STUDENTS  (UPPER ("NAME"))

In this example, UPPER ("NAME") is not an actual column. The database references this expression as an internal name, such as SYS_NC00008$. PROC METALIB fails to pair the index column with a physical column in the database because SYS_NC00008$ is not a physical column, and the Read access violation occurs.

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

A fix for SAS 9.1.3 (9.1 TS1M3) for this issue is available at:

A fix for SAS 9.1.3 (9.1 TS1M3) with Asian Language Support (DBCS) for this issue is available at:

A fix for this issue for Base SAS 9.21_M3 is available at: